Internet Info 1994 March

home *** CD-ROM | disk | FTP | other *** search

/ Internet Info 1994 March / Internet Info CD-ROM (Walnut Creek) (March 1994).iso / networking / terms / kermit / b / iktker.bwr < prev next >

Wrap

Text File | 1993-06-18 | 48.7 KB | 902 lines

TSO Kermit 4.2.x "Beware File" - Known Bugs, Problems, Limitations. As of: 18:10pm Thursday, 1993 June 17 This file contains (A) instructions for applying Kermit updates, (B) a list of unresolved problems, (C) a list of problems with work-arounds or optional fixes, and (D) a list of resolved problems. Bug reports should be sent to John Chandler <JCHBN@CUVMB.CC.COLUMBIA.EDU>. NOTE: entries will sometimes be entered under (D) even though the needed updates have not been released in IKTKER.UPD. Please check the date of the UPD file to see if it has been changed before requesting a new copy. Kermit-370 now carries an "edit" number in addition to the version and release numbers. The three numbers together are printed out in the assembly listing and displayed by Kermit at startup time. Be sure to include all three numbers (e.g., 4.2.4) along with any error reports. A) Update instructions ................................................. Many updates have been received since Kermit-TSO 4.1 was released. All updates prior to 90/4/14 have been removed from IKTKER.UPD and applied to the sources in the process of creating 4.2. If your source does not include the line defining &KVRSN to be 4.2, you should obtain an all-new source distribution from Columbia. Any updates created later than your source should be applied before you make the executable module. In general, updates received at Columbia will not be applied to the source files in the TSO Kermit distribution until and unless "major" bugs are uncovered, and then all accumulated updates will be applied at once. The description of each problem and a pointer to its solution will always be included in IKTKER.BWR (the present file), but the updates themselves are to be found in IKTKER.UPD. The procedure to update your copy of TSO Kermit is as follows: 1) Obtain the latest version of IKTKER.UPD, which contains all the updates as a composite file punctuated by comment lines introducing each update's name and briefly describing its purpose. Please note that some modes of file transport have a side effect of either doubling or removing any periods in the first column -- if your copy of IKTKER.UPD has records beginning with "/", then all instances of "/" in column 1 should be changed to "./", and all records with "@" in column 63 (introducing an update code normally found starting at column 64) should be moved over to make room for a "." in column 1. Similarly, any instances of ".." in columns 1-2 should be changed to just ".". A related problem can affect the sources by leaving a blank in column 80. That can happen via the loss of a "." in column 1 (in which case the sequence number will be shifted into columns 72-79) or via automated efforts to preserve the "." (in which case the sequence number will be truncated). The repair consists of inserting the missing "." in column 1 or "0" in column 80. 2) Determine the date of your sources. If you obtained the source from Columbia, the date is the value of the &KDATE variable symbol in the source itself, i.e., the release date of the current base version. If you received the source distribution from a secondary supplier, you will need to examine the code to determine the most recent update applied. Just sort the combined source by columns 67-71; the last line will be labeled with the last-applied update. 3) If your sources are "pure" Columbia 4.2, go on to step 4. Otherwise, you must take care to avoid applying updates that are already in the source. If it is inconvenient to obtain "pure" sources, you must go through the list of updates at the beginning of IKTKER.UPD and remove the entries for updates already included in (i.e., older than) your sources. Each line of the list begins with "./ *" plus an update code in the form xxyyddd (the yyddd is just the date of the update -- the list is arranged chronologically). Also, go through and discard those updates from the file. Each update begins with a second copy of the line from the list and goes to the next such line. The updates are also in chronological order. 4) Extract any desired optional updates from IKTKER.BWR (this file) and group them together with any local modifications specific to your site. NOTE: all updates in this file are indented one column to avoid all the transmission problems mentioned above in step 1. Be sure to shift everything over when you extract the updates. 5) Apply the updates to your composite source by running GUPI. There is a batch job in IKTKER.INS for installing Kermit from scratch, and the same job can be rerun as new updates become available. Simply omit job steps CNVASM through GUPLNK in subsequent runs. Note: Kermit uses the STATUS macro, which is sometimes found in SYS1.AMODGEN, instead of SYS1.MACLIB. Further note: be sure the macro libraries you use are compatible with the assembler -- at some installations, there is apparently a mismatch, such that the GETLINE macro has a definition with an "invalid" parameter name. Also, the GETLINE and STAX macros supplied with MVS/XA have been "modernized" to the extent that they cannot be used with the VS assembler. Further still, the GTSIZE macro is mangled at some sites and may require APAR OY22935. If you prefer, GUPI can be run interactively as a command processor. In that case, the updated source would still have to be assembled. In any case, you should not discard the original source because the updating process is simplest if you always start from the same base source. NOTE: step 5 requires that you have version 1.1 or later of GUPI, which in turn means that your sources must be no older than 88/9/15. ------------------------------------------------------------------------ B) Unresolved problems ................................................. ---------------- 88/3/9 ------------------------------------------------ An ABEND within a TSO command called from Kermit propagates back to the TMP, which then displays a READY message. Typing a carriage return will resume Kermit operation. ---------------- 89/1/20 ----------------------------------------------- Now that Kermit-370 supports multiple-filespec SEND, it is possible for a single SEND subcommand to specify overlapping wildcard filespecs. Only the CMS variant keeps track and makes sure that it doesn't send the same file twice within one send invocation. The others, including TSO Kermit-370, may send the same file again, and it is left to the user to prevent filename-collision problems on the receiving end. ---------------- 90/5/8 ------------------------------------------------ With a few exceptions, CONTROLLER will be set automatically when Kermit is invoked. See file IK0AAA.HLP in the Kermit distribution for a list of front ends that have been reported to allow Kermit file transfers and another list of reported failures. In those lists, CONTROLLER type VTAMTTY is omitted -- that being a peculiarity of TSO Kermit and the same as TTY, but needed when connected through TSO/VTAM if it does *not* have the IKTWTX1 exit. ---------------- 91/8/16 ----------------------------------------------- The type-out interception mechanism for server mode works only for "normal" line-oriented output, not for fullscreen applications. Indeed, since there is no mechanism provided for feeding subcommands to a program on the mainframe through the Kermit server, only one-shot, non- interactive commands should be issued via REMOTE HOST. ------------------------------------------------------------------------ C) Problems with workarounds or optional fixes ......................... If it becomes necessary to diagnose problems by turning DEBUG on, there may be trouble in handling the resulting KER.LOG dataset with certain tools, since the log is allocated with an LRECL equal to the largest allowed packet size. In practice, though, diagnostics can usually be done with short packets, so that the dataset can be copied with a truncated LRECL (e.g., 84). Even if long packets are present, it may be possible to truncate the records without losing the important details. ---------------- 88/3/9 ------------------------------------------------ The REMOTE COPY function of a Kermit-TSO server and the TYPE subcommand both require the TSO data utilities package available from IBM and other vendors. The necessary commands are COPY and LIST, respectively. If your system doesn't have them, it should be possible to create your own. For example, you can write CLIST's to reside in your CLIST library. ---------------- 88/3/9 ------------------------------------------------ While CLISTs may be invoked under Kermit, if they are called from within a TAKE file, they are not then executed until Kermit returns to command level. This means that a CLIST invoked from the system KERMINI file would execute after the user KERMINI. If such a CLIST is necessary, it would be advisable to comment out the first BAL 9,LUPTIN in USNTRF (to suppress the direct execution of the user KERMINI) and to add code to the end of the CLIST to execute the user KERMINI (if any). ---------------- 88/7/18 ----------------------------------------------- On some systems, TTY lines connected via VTAM are unable to carry long packets outbound because of the insertion of CRLF's every 130 bytes. When that is the case, it may be possible to circumvent the problem by applying the following update to the Kermit source (although the IBM documentation states that setting the line size to a value greater than 255 has unpredictable consequences). ./ * SC88200 - Correct line length problem ./ R 05904000 $ 5904000 1 STMSTY STSIZE SIZE=1920 Set up linesize @SC88200 ---------------- 89/2/27 ----------------------------------------------- The code for detecting the difference between SERIES1- and GRAPHICS-type terminal controllers may cause peculiar error messages at session startup, particularly if you wish to run Kermit on an IBM 3270- type terminal. Normally, Kermit can recover from these error conditions, but some configurations and/or versions of VTAM may hang the terminal session instead. For example, there may be an error message IKT00405I SCREEN ERASURE CAUSED BY ERROR RECOVERY from VTAM that never goes away. In that case, there are several possible cures. First is the simple expedient of pressing PA1 to clear the error condition. If that doesn't help at your site, you may find that logging onto the host via Netview's TAF component makes the error message appear only once. If you cannot persuade VTAM to be more sensible, you might want to bypass the code (especially if you don't have any GRAPHICS-type terminals). The code is governed by a set of switches which can be tailored to your needs: STCQBIT EQU X'01' WSF Query is always allowed STCQNS1 EQU X'02' WSF Q implies *not* SERIES1 STCS1 EQU X'04' Always assume SERIES1 STCNOS1 EQU X'08' Always assume *not* SERIES1 STCNORD EQU X'10' Asynch READ MOD is forbidden The standard flag value on TSO is STCQNS1; if you wish to force the code to select SERIES1, you should change that to STCS1, as in the following: ./ * SC9131X - Customize controller type selection ./ R 01158200 $ 1158200 100 11/21/91 00:16:50 &CONOPTS SETC 'STCS1' SETCON options @SC9131X Alternatively, if you have *only* GRAPHICS-type controllers, you could change it to STCNOS1. ---------------- 89/5/19 ----------------------------------------------- A mode of operation favored by some ISPF users is to keep files in one PDS, rather than scattered among a variety of PDS's and sequential files. In that mode of operation, Kermit TAKE files may not have a file extension of TAKE or KERMINI, but the user KERMINI file, in particular, must have a proper file extension in order to be recognized by Kermit at startup. For example, if each user had a PDS called ISPF.TEXT, and the user's KERMINI were expected to be member KERMINI of that PDS, the following update would make Kermit-TSO look in the right place (and also allow other TAKE files to be kept in ISPF.TEXT). ./ * SC89139 - Alternate location for init file ./ R 01122000 $ 1122000 500 05/19/89 18:14:55 USRTAKE DC C'ISPF.TEXT(KERMINI)' Init file @SC89139 ./ I 05215750 $ 5215760 10 05/19/89 18:14:55 CLC =C'.TEXT',3(1) Or is is .TEXT? @SC89139 BE RTRN0 That's ok too @SC89139 ---------------- 89/9/27 ----------------------------------------------- Kermit-TSO will recover data sets migrated using DFHSM, but not those archived by the ABR software. As a result, if the KERMINI files are no longer on-line, Kermit will simply miss them. The following update will cause data sets to be recovered as needed, provided Kermit has not already entered protocol mode. ./ * SC89270 - Recover ABR-migrated data sets. ./ D 06230140 06230180 09/27/89 16:32:40 ---------------- 90/3/1 ------------------------------------------------ On some systems, the leading DSN qualifier SYS1 is restricted, so that the system-wide Kermit INIT file cannot be cataloged as expected by Kermit-TSO. In such cases, the following update (or something similar) can be used to substitute the prefix of your choice. ./ * SC90060 - Alternate prefix for global init file ./ R 01120000 $ 1120000 100 03/01/90 18:20:29 SYSTAKE DC C'''SYS2' @SC90060 ---------------- 90/4/15 ----------------------------------------------- Some micro Kermits may garble the date/time stamp transmitted with files downloaded from TSO because there is only a date and not a time. As a matter of fact, some files have times as well (at sites with a system update that maintains a "modification date"), but many do not. This problem has been reported for some versions of ProComm, but MS-Kermit from Columbia is OK. There are two workarounds: switch micro Kermits or issue SET ATTR DATE OFF to TSO Kermit. ---------------- 90/5/11 ----------------------------------------------- If you feel it is too dangerous to allow a remote Kermit to issue a wildcard DELETE command to TSO Kermit, you can disable that feature via the following update. The effect is to treat any asterisk in a REMOTE KERMIT DELETE command as a number sign. Beware if you ever use a bare number sign as a DSN qualifier. ./ * SC90131 - Disable wildcard delete ./ D 05209100 05209200 05/11/90 19:08:38 ---------------- 90/7/5 ------------------------------------------------ Kermit-370 now honors the file type specification (binary or text) given by a sending Kermit in an Attribute packet. Old procedures for sending binary files may therefore not work properly anymore. To return to the old mode of operation, issue the subcommand SET ATTR TYPE OFF. To live with the new mode, be sure to issue the SET FILE TYPE to both sending and receiving Kermits (to be safe). ---------------- 90/7/30------------------------------------------------ When the file type is TEXT and the recfm is F, Kermit-370 strips off trailing blanks from each record before sending a file. In order to keep trailing blanks in a downloaded file, you can convert it to RECFM V in TSO before sending it, e.g., by using COPY with the RECFM VB option. This is true of versions from 4.1 onward. ---------------- 90/8/22 ----------------------------------------------- If, for some reason, the other Kermit insists on pretending ASCII bytes all have the 8th bit set, Kermit-370 will not detect the intended CRLF separators between lines. The result of uploading from such a Kermit is a (text) file with only one record. If the other Kermit cannot be fixed, the following update will make Kermit-370 treat ASCII 8D and 8A the same as 0D and 0A, as long as the ATOE table does so. ./ * SC90151 - Forgive 7-bit ASCII files with 8th bit on ./ I 02490500 $ 2490700 200 08/03/90 16:06:46 ISW78 DC X'7F' Start with 7-bit ASCII @SC90151 ./ I 02713500 $ 2713700 200 08/03/90 16:06:46 SW78 DS X'7F' Switch for 7-bit/8-bit ASCII @SC90151 ./ I 03436000 $ 3436500 500 06/01/90 13:24:03 KCALL TBLCRLF Note current treatment @SC90151 ./ I 03442000 $ 3442500 500 06/01/90 13:24:03 KCALL TBLCRLF Note current treatment @SC90151 ./ I 04318000 $ 4318500 500 06/01/90 13:24:03 KCALL TBLCRLF Reset 7-bit/8-bit mask for CRLF @SC90151 ./ I 04386000 $ 4386080 80 06/01/90 13:24:03 * * Entry: nothing special @SC90151 * Exit: SW78 set up correctly @SC90151 TBLCRLF ENTER ALT @SC90151 MVI SW78,255 Assume 8-bit codes @SC90151 CLC ATOE+ALF(1),ATOE+ALF+128 @SC90151 BNE RTRN0 @SC90151 CLC ATOE+CR(1),ATOE+CR+128 @SC90151 BNE RTRN0 @SC90151 MVI SW78,127 No, 7-bit codes @SC90151 B RTRN0 @SC90151 ./ I 08048000 $ 8048400 400 NC CUR,SW78 If 7-bit ASCII, ignore 8th bit @SC90151 ---------------- 91/1/4 ------------------------------------------------ There may be problems with timing that can be avoided by removing the capability to timeout from the mainframe side as in the following optional update. This update is part of the official release of Kermit for ROSCOE and, in that environment, avoids multiprocessing abends. ./ * SC91004 - ROSCOE IDENTIFY problem and FULLSCREEN timeouts (TSO) ./ D 01127090 01127900 01/31/91 23:12:22 ./ R 05704000 05721000 $ 5704000 1000 01/31/91 23:12:22 L 0,4(,1) Size of TGET buffer @SC92030 L 1,0(,1) Adr of buffer to put in @NW86330 TGET (1),(0),ASIS @NW86330 LTR 15,15 @NW86330 BZ TRMRET Ok @SC91004 C 15,F12 @NW86330 BE TRMRET Ok @SC92030 CH 15,=H'24' @SC92030 BNE RTRNM1 Signal I/O error @SC91004 TRMRET ST 1,KTGETT+4 Store length read @SC92030 ./ D 05723000 05729000 01/31/91 23:12:22 ./ D 05740000 05774000 01/31/91 23:12:22 ./ D 05919000 05928000 01/31/91 23:12:22 ./ D 05957000 04/11/91 15:25:18 ---------------- 91/9/18 ----------------------------------------------- There is a report of IKT00405I errors (see optional update SC9131X) in situations that have nothing to with unexpected controller types. For example, the screen erasure error may occur in interactive mode if a Kermit subcommand is entered on the last line of the screen. Pressing PA1 appears to clear the error condition. ---------------- 91/11/21 ---------------------------------------------- In order to change the default Kanji encoding from IBM-style to another, add one of the following updates. ./ * SC9132X - Change Kanji default ./ R 01411560 $ 1411560 10 11/21/91 @SC9132X &KNJDEF SETC 'HITACHI' Default Kanji @SC9132X ./ * SC9132X - Change Kanji default ./ R 01411560 $ 1411560 10 11/21/91 @SC9132X &KNJDEF SETC 'FUJITSU' Default Kanji @SC9132X ---------------- 92/4/10 ----------------------------------------------- The minimum size of strings to be subjected to run-length encoding may need to be changed to two to make the new FULLSCREEN mode work on certain protocol converters, such as the MICOM 7400, which convert three successive blanks into cursor motion commands (or even two!). The following update accomplishes that. ./ * SC92101 - Encode multiple blanks ./ I 07929000 $ 7929050 50 04/10/92 17:35:12 CLI 0(8),ABL Is it a blank? @SC92101 BNE ENCRP1 No, use normal criterion @SC92101 C 14,F2 @SC92101 BNL ENCRP2 Always encode multiple blanks @SC92101 ENCRP1 DS 0H @SC92101 ./ I 07929600 $ 7929800 200 04/10/92 17:35:12 ENCRP2 DS 0H @SC92101 ---------------- 92/10/18 ---------------------------------------------- When Kanji characters are first selected, the default for the single- byte character set is CP290 (hard-coded in Kermit-370). That can be changed, however: ./ * SC92252 - Make CP281 the default SBCS with KANJI ./ R 04448600 $ 4448600 100 10/18/91 20:52:19 TBVJP DC CL(LALF)'CP281',CL(LALF)'CP500',CL(LALF)'CP290' @SC92252 ---------------- 93/1/21 ----------------------------------------------- Kermit-370 in FULLSCREEN mode can be at the mercy of clever efforts toward screen "optimization" by the protocol converter. One possible symptom is the suppression of the last outbound packet in a transfer if the screen is cleared just afterwards. This may happen after an upload or upon leaving server mode. To avoid this possibility, Kermit-370 can simply wait a few seconds to give the protocol converter less excuse for suppressing the last packet. The following update uses four seconds, but the optimum time may be more or less, depending on the system. ./ * SC93021 - Try to prevent end effect in FULLSCREEN mode ./ I 08645400 $ 8645500 100 01/22/93 12:31:55 CLI TRMTP,C'F' @SC93021 BNE INTINICN Go if not FULLSCREEN @SC93021 LA 0,4 Wait four seconds to synchronize @SC93021 KCALL SUPFNC,9 @SC93021 INTINICN DS 0H @SC93021 ---------------- 93/4/15 ----------------------------------------------- Kermit-TSO now has to face three different linemode environments: the original non-VTAM line (now seldom seen), normal VTAM LU1 lines, and a new class of SNA 3770-type lines. Kermit automatically handles the first two types by adopting the proper terminal I/O method to get the necessary control characters out. These are reflected in the TTY and VTAMTTY settings for CONTROLLER in Kermit. Unfortunately, vanilla VTAM does not let any control characters out for the third type (except, possibly, BEL). Therefore, Kermit can work only when VTAM has been equipped with one of two exit routines, IKTRTX1 or IKTWTX1. If the latter is installed (and many sites have it), VTAMTTY is not needed at all, and TTY will serve for all three types of linemode sessions. The following update disables the automatic selection of VTAMTTY. ./ * SC93105 - Disable VTAMTTY selection: IKTWTX1 installed (TSO) ./ D 05904900 Alternatively, either with or without IKTWTX1, VTAM will permit control characters through the third class of lines when the IKTRTX1 exit is installed. Apparently, the widely used version of IKTWTX1 distributed by the SAS Institute will work when simply renamed IKTRTX1. Also, the following code will serve. IKTRTX1 CSECT USING *,15 TM 9(1),X'30' CHECK TPUT OPTION BNM RTRN0 NOT CONTROL - ALLOW EDITING TM 9(1),X'20' BZ RTRN0 NOT CONTROL LA 15,4 CONTROL - NO EDITING BR 14 RTRN0 SR 15,15 BR 14 END ------------------------------------------------------------------------ D) Resolved problems ................................................... ---------------- 90/5/8 ------------------------------------------------ A commonly reported "problem" is that Kermit-TSO objects to a send packet size greater than 94, and users wonder how to turn on long-packet protocol for downloads. The answer is that the the maximum packet size in Kermit protocol is always dictated by the receiving Kermit -- ALWAYS. NOTHING YOU CAN SAY TO A SENDING KERMIT WILL EVER MAKE IT SEND PACKETS LONGER THAN THE RECEIVING KERMIT ASKS FOR. Conversely, Kermit-TSO will always use packets as long as possible unless frequent transmission errors indicate a noisy communication line. The only purpose for the send packet-size parameter in Kermit-TSO is to set the default, in case the receiving Kermit is badly crippled (in which case, long packets are entirely out of the question anyway), or to control "raw" downloads (those without Kermit protocol and parameter negotiation). ---------------- 90/5/8 ------------------------------------------------ Kermit-370 is often faced with a communication front end that treats an XOFF from the other end as an end-of-line. Thus, in server mode, it may receive "packets" consisting of XON XOFF or just XOFF when the micro issues flow control for purely precautionary reasons. Such packets are now ignored, rather than treated as invalid server commands. The fix: SC90106. ---------------- 90/5/14 ----------------------------------------------- Kermit-370 is now careful not to attempt to send packets longer than the (system-specific) maximum. The fix: SC90134. ---------------- 90/5/30 ----------------------------------------------- Kermit-TSO now uses the ISPF modification date, if available, when sending the attributes of a PDS member. The fix: SC90139. ---------------- 90/5/30 ----------------------------------------------- The TPG macro has been changed in IBM's latest system releases, and the invocation in Kermit-TSO has been changed accordingly to be compatible with both the old and new forms. The fix: SC90145. ---------------- 90/5/30 ----------------------------------------------- The length of the BLDL for possible command processors has been extended so that system commands can be executed properly from within Kermit-TSO. The fix: SC90149. ---------------- 90/5/30 ----------------------------------------------- Kermit-370 now accepts PACKET-LENGTH as an alias for PACKET-SIZE in SET SEND or SET RECEIVE. The fix: SC90150. ---------------- 90/6/10 ----------------------------------------------- Kermit-370 now supports transfers in LATIN2 and LATIN3 and file storage in CP870, CP880, and CP905. In addition, L1, L2, and L3 are recognized as aliases for the three LATIN sets, and two-character abbreviations are accepted for the other transfer sets as well. The new sets add support for Afrikaans, Albanian, Catalan, Croatian, Czech, Esperanto, Galician, Hungarian, Maltese, Polish, Romanian, Slovak, Slovene, and Turkish. The fix: SC90152. ---------------- 90/6/22 ----------------------------------------------- Kermit-370 supports file transfers through the IBM 3174 AEA with level 2 microcode in configuration B. The support is restricted to terminal types defined in the 3174 to have ASCII Graphics capability. That capability is available by default only for VT241 and Tektronix 4205 terminals, but user-defined terminal types are also possible. Also, the Graphics capability is allowed only for lines defined without associated Host Addressible Printers. Kermit-370 now automatically detects the B2 AEA and sets CONTROLLER accordingly (to AEA if Graphics is allowed, to NONE if not). However, if the 3174 is owned by VTAM, and the connection is made with a logmode that forbids the Read Partition Query (such as M2SDLCNQ), Kermit cannot detect the AEA and will default to CONTROLLER GRAPHICS (and, incidentally, cannot transfer files even with CONTROLLER set to AEA by hand). M2SDLCQ is known to allow correct operation, but other logmodes have not been tested. Since the 3174 supports full 8-bit communication, it may be useful to configure the ports for 8-bit data and to set both SEND and RECEIVE PARITY to NONE in Kermit-370. The fix: SC90173. Note: B2 microcode became available from IBM in May 1990. B3 followed soon afterward, and it supports file transfer the same way as B2. ---------------- 90/6/28 ----------------------------------------------- Kermit-370 now gives correct status reports after an XTYPE, rather than retaining the error code, if any, from a previous transfer. Also, XTYPE now supports the full, extended syntax of SEND. The fix: SC90179. ---------------- 90/7/30 ----------------------------------------------- Kermit-370 now uses the FILE COLLISION settings for all files in a group rather than just the first. The fix: SC90211. ---------------- 90/8/14 ----------------------------------------------- When DEBUG is set to I/O, Kermit-TSO includes in KER.LOG a hex dump of the data buffer as well as the I/O parameter list for fullscreen terminal types. The old behavior of including the AID and buffer addresses has been superseded. Also, a new LONG option is now available for DEBUG to request hex dumps of up to 200 bytes, instead of only 24. The fix: SC90222. ---------------- 90/8/27 ----------------------------------------------- Kermit-370 now has three new subcommands: REMOTE MAIL, REMOTE PRINT, and REMOTE SUBMIT. They transmit a file (or group of files via wild cards) tagged for mailing, printing, and submitting as job, respectively. The syntax is: REMOTE MAIL/PRINT/SUBMIT filespec options The options are passed to the receiving Kermit and must be in a format it will understand. The fix: SC90239. ---------------- 90/8/27 ----------------------------------------------- Kermit-TSO is now at level 4.2.1. The fix: SC90240. ---------------- 90/9/7 ------------------------------------------------ Kermit-370 now has a TRANSPARENT transfer character set, which applies a null translation to all incoming and outgoing files. The fix: SC90250. ---------------- 90/9/27 ----------------------------------------------- Kermit-370 failed to use control-quoting on 8-bit analogs of ordinary control characters if 8th-bit quoting was turned off. The fix: SC90270. ---------------- 90/9/27 ----------------------------------------------- Kermit-370 now suppresses echoing in protocol mode on LU1 3770-type front ends by sending Inhibit/Enable Presentation controls (EBCDIC x'24' and x'14'). These characters should have no effect on "old-fashioned" linemode equipment. The fix: 2L90270. ---------------- 90/9/28 ----------------------------------------------- Some corrections to the Cyrillic translation tables. The fix: SC90271. ---------------- 90/10/2 ----------------------------------------------- The change that allowed Kermit-TSO 4.1 to handle uncataloged datasets had the side effect of making all uploads of new datasets land on arbitrary volumes unless a particular volume was specified. Now, such uploads again go to the default group specified in the user's profile, or to the unit and/or volume, if any, specified to Kermit. Moreover, specifying a volume to Kermit implies a unit of SYSALLDA regardless of how the unit is set. The fix: SC90275. ---------------- 90/10/4 ----------------------------------------------- Kermit-370 now keeps separate limits on packet buffer sizes for linemode and fullscreen devices and no longer assumes that the latter is always bigger. The fix: SC90277. ---------------- 90/10/5 ----------------------------------------------- Kermit-370 now has a SET TTABLE KP option which enables a full 8-bit translation table based on Hollerith codes. The fix: SC90278. ---------------- 90/10/12 ---------------------------------------------- Kermit-370 now allows testing with a packet character that is not a control character without requiring that the test character be avoided in the data. The fix: SC90285. ---------------- 90/10/16 ---------------------------------------------- Kermit-370 now leaves server mode if packet I/O errors recur. The fix: SC90289. ---------------- 90/10/19 ---------------------------------------------- The extraneous B packet after an XTYPE (introduced in 4.2.1) is now avoided. The fix: SC90292. ---------------- 90/12/4 ----------------------------------------------- V-binary (or D-binary) file transfers trash the last 2 (or 5) bytes of any record of 32756 bytes. The fix: SC90338. ---------------- 90/12/5 ----------------------------------------------- Kermit-370 now has a VERSION subcommand, which displays the version number and date. The fix: SC90339. ---------------- 91/1/8 ------------------------------------------------ Kermit-370 now has a facility for taking snapshot dumps of selected storage blocks during execution and another for tracing events. See SET DEBUG in the User's Guide for more details. The fixes: SC91008 and LM91008. ---------------- 91/1/17 ----------------------------------------------- Kermit-370 now generates a more informative error message if an attempt to open a file for output fails. The fix: SC91017. ---------------- 91/2/1 ------------------------------------------------ Kermit-370 now interprets the terminal input more liberally when looking for possible STOP commands in protocol mode. If the word STOP appears in either upper- or lower-case EBCDIC, rather than ASCII, it is accepted as a valid STOP. This can be useful in recovering from an attempt to start a tranfer through a device that has no transparent mode. The fix: SC91032. ---------------- 91/2/8 ------------------------------------------------ Certain kinds of lock-up are now avoided. The fix: SC91039. ---------------- 91/3/5 ------------------------------------------------ Kermit-370 now displays any extra explanatory error message (such as those for I/O errors) along with the basic message upon completing a subcommand. The fix: SC91064. ---------------- 91/3/8 ------------------------------------------------ Support for lower-case Roman letters has been added to CP290 (Katakana). Some corrections have been made to the LATIN2-to-CP870 table. The fix: SC91067. ---------------- 91/4/4 ------------------------------------------------ Kermit-370 now processes any incoming Date attribute for validity, even though no variant currently uses it. The fix: SC91094. ---------------- 91/4/9 ------------------------------------------------ Kermit-370 now supports an "End-of-attributes" attribute. There is no current application, but its existence should facilitate negotiation of file attributes when it becomes generally supported by other Kermits as well. If another Kermit objects to the new attribute (not likely), you can suppress it by typing SET ATT END OFF. The fix: SC91109. ---------------- 91/4/26 ----------------------------------------------- Kermit-370 now supports a "CC" option along with the line range for sending files. This option specifies that the file has carriage control in column 1 and that it should be converted to ASCII control characters. For example: SEND filespec<_CC> (the underscore is the option delimiter and indicates here that no line range is given). The fixes: SC91116 and SC91224. ---------------- 91/5/1 ------------------------------------------------ Kermit-TSO now allows multiple subcommands to be entered on the initial command line, separated by the Kermit delimiter, which must be defined in one of the initialization files. All such subcommands will now be executed in turn before Kermit quits and returns. The fix: SC91121. ---------------- 91/6/14 ----------------------------------------------- Kermit-370 now stops attempting to cancel a received file via the "YX" method after ten tries have been ignored by the sender. At that point, it issues an E-packet saying "Transfer cancelled". The fix: SC91165. ---------------- 91/6/21 ----------------------------------------------- Kermit-370 now records the time of starting each file transfer in the transaction log. Also, the error message for a cancellation includes the reason (if known), both in the transaction log and in error packets. Further, there is a new DEBUG option TIME that causes a time tag to be inserted into each I/O debug log record. The fix: SC91172. ---------------- 91/6/29 ----------------------------------------------- Kermit-370 now supports 8th-bit quoting for the XECHO subcommand, using the same prefix character as in Kermit protocol. The quoting can, thus, be turned off. The fix: SC91180. ---------------- 91/7/10 ----------------------------------------------- Kermit-370 now avoids a long-standing "hidden" bug: transfers no longer fail if DEBUG is set to RAW while long packets are in use. The fix: SC91191. ---------------- 91/7/17 ----------------------------------------------- Kermit-370 now mentions REMOTE PRINT in the remote help display. The fix: SC91198. ---------------- 91/7/24 ----------------------------------------------- Kermit-TSO now makes the current status code available to CLIST's as &LASTCC. The fix: SC91205. ---------------- 91/8/19 ----------------------------------------------- Kermit-370 is now at level 4.2.2: SC91231. ---------------- 91/9/3 ------------------------------------------------ Kermit-TSO 4.2.1 introduced a bug in the procedure for clearing the screen to get the SHOW ALL display on one screen. The fix is included in version 4.2.2: SC91246. ---------------- 91/9/4 ------------------------------------------------ Kermit-370 no longer halts a transfer upon seeing a data packet with no data. The fix: SC91247. ---------------- 91/9/13 ----------------------------------------------- Kermit-370 now allows the STOP command on PCI and certain other protocol converters that did not previously support it. The fix: SC91256. ---------------- 91/9/16 ----------------------------------------------- Kermit-TSO no longer generates a KER.LOG entry marked "e" for normal full-screen I/O operations. The fix: SC91259. ---------------- 91/9/20 ----------------------------------------------- Kermit-370 no longer gives a spurious reason for a cancellation issued by user intervention on the micro. The fix: SC91263. ---------------- 91/10/2 ----------------------------------------------- Kermit-370 supports locking shift protocol (helps to compress certain files with many 8-bit bytes). The fix: SC91275. ---------------- 91/10/8 ----------------------------------------------- Kermit-370 now avoids looping when a solid terminal I/O error sets in or upon any error at the very end of a transfer (no reply expected). The fix: SC91281. ---------------- 91/10/10 ---------------------------------------------- Kermit-TSO now recovers cleanly if the user specifies an erroneous CWD string. The fix: SC91283. ---------------- 91/10/11 ---------------------------------------------- Kermit-370 now uses the built-in default A-to-E translation table for interpreting Kermit commands in server mode when the transfer character set is TRANSPARENT. The fix: SC91284. ---------------- 91/10/22 ---------------------------------------------- Kermit-370 now suggests changes in some settings if the initialization file(s) haven't adopted the new-and-better values. This avoids changing the built-in defaults. The fix: SC91295. ---------------- 91/11/7 ----------------------------------------------- Kermit-TSO now determines in advance whether a terminal could possibly be attached to a 3174 AEA before attempting to confirm that, since the attempt itself is risky. The terminal type detection code has been moved to the generic part of Kermit-370, except for a few flags that define system-specific limitations. The tried-and-true optional update SC89058 has been revised and renamed SC9131X accordingly (see above the note dated 89/2/27). The fix: SC91311. ---------------- 91/11/8 ----------------------------------------------- Kermit-370 now has a SIMULATE subcommand, which plays back a file giving one or both sides of a file transfer to supply the packets (instead of the communication line). This facilitates testing new protocol features one Kermit at a time. Lines in the "canned" file are ignored if they begin "S:", are translated from EBCDIC to ASCII if they begin "R:", and are taken as "raw" I/O otherwise. SIMULATE automatically reverts to normal packet I/O either at the end of the file or upon detection of an error. The filespec has the same defaults as for the TAKE subcommand. The fix: SC91312. ---------------- 91/11/12 ---------------------------------------------- Kermit-370 now tolerates alternate EBCDIC versions which do not have all the Roman letters at the standard code points. If the source is passed though a filter that consistently translates certain characters to other code points, the resulting executable program will adopt the same convention, and upcasing and downcasing will follow the new pattern. In particular, this may be necessary in Japan on systems that use the codes normally attached to lower-case Roman letters for Katakana. The fix: SC91316. ---------------- 91/11/16 ---------------------------------------------- The language-specific use of one-letter abbreviations of SET options for program logic flow has been generalized by selecting the internal codes independently of the names of the external options. Any given option could, in principle, be renamed without requiring changes outside of the option keyword table itself. In particular, the keywords could all be translated to a language other than English. Character sets names are an exception, and accented letters should be avoided unless the upcasing and downcasing tables are extended appropriately (see SC91316 above). The fix: SC91320. ---------------- 91/11/21 ---------------------------------------------- Kermit-370 now supports file transfers using Japanese Kanji with translation between IBM, Hitachi, or Fujitsu codes and the newly added transfer character set JAPAN-EUC. Since the new translations require large tables, they have been isolated in a new section of the source code IK0KAN.ASM, which can be omitted. The fix: SC91325. Kanji text differs from other kinds of text files in that it has *two* different character sets associated with it, a single-byte character set (SBCS) and a double-byte character set (DBCS). Thus, it may be necessary to specify the subcommand SET FILE CHARACTER-SET twice: first, for the SBCS and, second, for the DBCS. For example, SET FIL CH CP290 and SET FIL CH FUJ would select one possible SBCS (CP290) along with the Fujitsu double-byte set. Other possible SBCS's are CP281, CP500, and H-EBCDIK-DASH. Plain "EBCDIC" is not currently allowed in combination with Kanji. It is important to specify the single-byte character set first. Note: the chosen SBCS may result in EBCDIC/ASCII translations that differ from those performed by the communications front (for non-transparent modes) -- in that case, it is necessary to SET TTABLE ON in order to transfer files. ---------------- 91/12/18 ---------------------------------------------- Kermit-370 has supported file transfer through the IBM 3174 AEA since release 4.2.1, but some conditions could hang a session after finishing a download. The fix: SC91352. ---------------- 92/1/30 ----------------------------------------------- Kermit-370 has a new FULLSCREEN controller type (the same name as a type that already existed, but served as a synonym for VTAMTTY for historical reasons). The new mode allows Kermit file transfers in a generic way on many different kinds of protocol converters, but it carries some special limitations -- packets cannot be longer than 80 bytes, and the other end must be MS-Kermit 3.12 or higher or possibly C-Kermit 5A.179 or higher. See IK0423.HLP for details on the new mode. The fix: SC92030. ---------------- 92/1/31 ----------------------------------------------- Kermit-370 is now careful to say "unknown" as the reason for cancelling a transfer halted by typing STOP. The fix: SC92031. ---------------- 92/2/21 ----------------------------------------------- The minimum size of strings to be subjected to run-length encoding has been made into a parameter in the Definitions section. The default setting, as before, is 3. Changing it to 2 may be needed to make the new FULLSCREEN mode work on certain protocol converters, such as the MICOM 7400, which convert three successive blanks into cursor motion commands (or even two!). See part C above for such an update. The fix: SC92052. ---------------- 92/3/4 ------------------------------------------------ Getting out of server mode by entering STOP no longer requires hitting ENTER an extra time. The fix: SC92064. ---------------- 92/3/12 ----------------------------------------------- The Hydra II tends to lock up upon receiving an Erase-Write command with no data. Kermit-370 formerly used such a command to condition the screen for an XECHO or XTYPE or to start Kermit protocol mode when DELAY was set to 0. The problem is now avoided by including a single blank in such cases. The fix: SC92072. ---------------- 92/3/13 ----------------------------------------------- Kermit-TSO now properly senses the QUERY bit, previously always deemed to be off (see SC91311 above). The fix: DL92073. ---------------- 92/3/25 ----------------------------------------------- Kermit protocol now includes a special checksum type called BLANK-FREE-2 intended to avoid the possibility of multiple blanks in Kermit packets. This can be necessary in FULLSCREEN mode for certain types of protocol converter, such as the MICOM 7400. The fix: SC92085. ---------------- 92/4/22 ----------------------------------------------- Kermit-370 now supports synonym CP1047 for the default file character set EBCDIC, following IBM recognition of the de facto standard and the registration of that character set. The fix: SC92113. ---------------- 92/4/29 ----------------------------------------------- Kermit-370 has changed the calling sequence of the KERMAIL, KERMPRT, and KERMSUB commands that it invokes in support of local mail, print, and job submission. At the first invocation (for verifying that the desired operation is feasible), Kermit passes a dummy filespec consisting of the single character "." instead of passing none at all. The fix: SC92120. Implementers take note! ---------------- 92/5/13 ----------------------------------------------- Kermit-TSO is now at level 4.2.3. The fix: SC92134. ---------------- 92/5/26 ----------------------------------------------- Kermit-TSO now supports relative generation numbers for GDG's both for sending and receiving files. The standard notation of (0) represents the current generation, (-n) represents "n" generations back, and (+1) represents the next generation. There is no support for specifying the concatenation of all existing generations as one file. Kermit-TSO is now at level 4.2.4. The fix: GA92147. ---------------- 92/6/10 ----------------------------------------------- Kermit-370 now appends an extra message to the normal protocol-mode greetings, provided DELAY is at least 2. The extra message is of the form "KERMIT READY TO SEND..." (or RECEIVE or SERVE). The fix: SC92161. ---------------- 92/6/17 ----------------------------------------------- Kermit-370 has a new TDUMP option available when the assembly-time TRACE option is enabled. Specifying TDUMP TRACE prints a dump of the trace table. Note that the new option is permitted only if TRACE is enabled. The fix: SC92169. ---------------- 92/6/26 ----------------------------------------------- In order to satisfy the restrictions of the F assembler (still used at many sites running CICS under VSE), the TITLE and PRINT ops at the start of open code have been moved after the definitions of global variable symbols. The fix: SC92178. ---------------- 92/8/20 ----------------------------------------------- Kermit-370 now supports the Thai character set. The fix: SC92233. ---------------- 92/12/7 ----------------------------------------------- Kermit-TSO can hang in server mode if the client sends a REMOTE DIR request for a data set that doesn't exist. The fix: SC92342. ---------------- 92/12/17 ---------------------------------------------- Kermit-370 now uses TTABLE logic for both the DEBUG and SIM subcommands. The fix: SC92352. ---------------- 93/1/14 ----------------------------------------------- Kermit-370 now prints a nominal efficiency rating in the STATUS report if SPEED is defined. The fix: SC93014. ---------------- 93/6/8 ------------------------------------------------ Kermit-TSO now uses the recovery procedure from the CMS variant to get around 7171 line overrun problems. The fix: SC93159. ------------------------------------------------------------------------